Add an explanation about using opaque types on classes #11328
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@odersky is this something that you had in mind when you asked about docs? |
SethTisue
reviewed
Feb 5, 2021
| @@ -133,4 +133,34 @@ end User | |||
| On the other hand, the call `roItem.rights.isOneOf(ReadWrite)` would give a type error | |||
| since `Permissions` and `PermissionChoice` are different, unrelated types outside `Access`. | |||
|
|
|||
|
|
|||
| ### Opaque Type Members on Classes | |||
| While typically, opaque types are used toghether with objects to hide implementation details of a module, they can also be used with classes. | |||
odersky
approved these changes
Feb 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds an explanation that opaque types can also be used on classes and mentions the intuition as requested by @odersky in #11277.